[202412][PR #21956]disable ipv6 for broadcom SONiC fanout devices.#969
Merged
r12f merged 1 commit intoAzure:202412from Feb 24, 2026
Merged
[202412][PR #21956]disable ipv6 for broadcom SONiC fanout devices.#969r12f merged 1 commit intoAzure:202412from
r12f merged 1 commit intoAzure:202412from
Conversation
12 tasks
Contributor
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Cherry-pick sonic-net/sonic-mgmt#21956 into 202412
Description of PR
Summary:
Fixes test_qos_sai failures due to unexpected ipv6 packets coming from fanout device
Type of change
Back port request
Approach
What is the motivation for this PR?
Disable ipv6 for broadcom SONiC fanout devices.
How did you do it?
Add broadcom into the list.
How did you verify/test it?
physical testbed.
Any platform specific information?
Supported testbed topology if it's a new test case?
Documentation